Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Oct 1, 2025

Automated Release PR

0.13.0 (2025-10-03)

Full Changelog: v0.12.0...v0.13.0

Features

  • Http proxy (2664172)
  • Update oAPI and data model for proxy status (014d704)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions


TL;DR

This is an automated release that bumps the package version to 0.13.0 and introduces a new HTTP proxy feature.

Why we made these changes

This release adds support for HTTP proxies and updates the associated API data models to reflect the new functionality.

What changed?

  • The package version has been updated to 0.13.0 in pyproject.toml, CHANGELOG.md, and src/kernel/_version.py.
  • Data models for proxy creation, listing, and retrieval have been updated (proxy_create_response.py, proxy_list_response.py, proxy_retrieve_response.py).
  • The release manifest (release-please-manifest.json) and project stats (stats.yml) have been updated accordingly.

Validation

This is an automated release PR, and validation is handled by the CI pipeline.

Description generated by Mesa. Update settings

@stainless-app
Copy link
Contributor Author

stainless-app bot commented Oct 1, 2025

🧪 Testing

To try out this version of the SDK, run:

pip install 'https://pkg.stainless.com/s/kernel-python/266417290f174a560ad0f820a22efb3c2eb35a67/kernel-0.12.0-py3-none-any.whl'

Expires: Sun, 02 Nov 2025 17:28:12 GMT

Copy link

@mesa-dot-dev mesa-dot-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Performed full review of 6d87563...e2e4589

Analysis

  1. The PR is adding proxy health monitoring features but relies entirely on auto-generated code from OpenAPI specs, which may limit customization possibilities if special handling is needed for edge cases.

  2. While Optional fields ensure backward compatibility, the PR doesn't indicate if there's validation logic to ensure these new status fields are consistently populated across all proxy operations.

  3. The restricted literal type for the status field (available/unavailable) may be too simplistic for comprehensive health monitoring - consider if additional states might be needed in the future (degraded, maintenance, etc.).

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

Slash Commands:

  • /review - Request a full code review
  • /review latest - Review only changes since the last review
  • /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
  • /help - Get help with Mesa commands and configuration options

8 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from e2e4589 to 1f9126d Compare October 3, 2025 17:27
@stainless-app stainless-app bot merged commit 6fa28e3 into main Oct 3, 2025
7 checks passed
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Oct 3, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants